FluxCD MCP Server

@Stefan Prodan

Visit Server

7 months ago

# kubernetes

# gitops

# devops

AI-Assisted GitOps for Kubernetes clusters managed by Flux CD

Overview Tools Comments

Overview

The Flux MCP Server connects AI assistants to Kubernetes clusters manged by Flux Operator, enabling seamless interaction through natural language. It serves as a bridge between AI tools and GitOps pipelines, allowing you to analyze deployment across environments, troubleshoot issues, and perform operations using conversational prompts.

Using AI assistants with the Flux MCP Server, you can:

Debug GitOps pipelines end-to-end from Flux resources to application logs
Get intelligent root cause analysis for failed deployments
Compare Flux configurations and Kubernetes resources between clusters
Visualize Flux dependencies with diagrams generated from the cluster state
Instruct Flux to perform operations using conversational prompts

Quickstart

Install the Flux MCP Server using Homebrew:

brew install controlplaneio-fluxcd/tap/flux-operator-mcp

For other installation options, refer to the installation guide.

Add the following configuration to your AI assistant's MCP settings:

{
  "flux-operator-mcp":{
    "command":"flux-operator-mcp",
    "args":[
      "serve",
      "--read-only=false"
    ],
    "env":{
      "KUBECONFIG":"/path/to/.kube/config"
    }
  }
}

Replace /path/to/.kube/config with the absolute path to your kubeconfig file, you can find it with: echo $HOME/.kube/config.

Copy the AI rules from instructions.md and place them into the appropriate file for your assistant.

Restart the AI assistant app and test the MCP Server with the following prompts:

"Which cluster contexts are available in my kubeconfig?"
"What version of Flux is running in my current cluster?"

For more information on how to use the MCP Server with Claude, Cursor, GitHub Copilot, and other assistants, please refer to the documentation website.

Documentation

License

The MCP Server is open-source and part of the Flux Operator project licensed under the AGPL-3.0.

Try in Playground

Server Config

{
  "mcpServers": {
    "flux-operator-mcp": {
      "command": "flux-operator-mcp",
      "args": [
        "serve",
        "--read-only=false"
      ],
      "env": {
        "KUBECONFIG": "/path/to/.kube/config"
      }
    }
  }
}

Build with ShipAny.